Mobile phone ATM processing methods and systems

ABSTRACT

Embodiments provide systems, methods, processes, computer program code and means for using mobile devices to conduct transactions with ATM devices.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is related to, and claims benefit to and priority ofU.S. Patent Application Ser. No. 61/426,731, filed on Dec. 23, 2010 andU.S. patent application Ser. No. 12/846,911, the contents of each ofwhich are hereby incorporated by reference in their entirety for allpurposes.

BACKGROUND

Automated Teller Machines (“ATMs”) have been in use for years, andconsumers rely on their ability to access cash around the world at thesedevices. In a typical ATM transaction, a consumer inserts a plastic cardinto a card reader of the ATM and the ATM reads information from amagnetic stripe on the card or a chip embedded in the card. Theinformation is used to establish communication with a financialinstitution associated with the consumer's financial account, and theconsumer is then prompted to enter a personal identification number(“PIN”) or other verification information. Once verified, the consumeris able to select an amount of cash (subject to account limits andbalance) to receive from the ATM. The process is simple and relativelysecure, and consumers around the world are used to the process.

Increasingly, however, consumers wish to conduct transactions withoutplastic payment cards. For example, the inventor of the instantapplication described systems and methods for using mobile devices (suchas mobile phones) to conduct purchase transactions at merchant in U.S.patent application Ser. No. 12/846,911, filed on Jul. 30, 2010, thecontents of which are hereby incorporated herein in their entirety forall purposes.

It would be desirable to allow consumers an ability to interact with ATMdevices using their mobile device (such as a mobile phone) to withdrawcash or to conduct other transactions at the ATM.

These, and other, problems are solved by using systems and methods ofthe present invention. Other advantages and features will becomeapparent upon reading the following disclosure.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram depicting a transaction system configuredpursuant to some embodiments.

FIG. 2 is a block diagram depicting further details of a transactionsystem configured pursuant to some embodiments.

FIGS. 3-6 are sample user interfaces associated with embodiments of thepresent invention.

FIG. 7 is a block diagram depicting features of a mobile device pursuantto some embodiments.

FIG. 8 is a flow chart depicting a process pursuant to some embodiments.

DESCRIPTION

Embodiments of the present invention relate to systems, methods,processes, computer program code, and means for using mobile devices toconduct transactions with ATM devices or other cash dispensing devices(hereinafter referred to simply as “ATM devices” or “ATMs”). In someembodiments, a mobile device configured using features of the presentinvention may be capable of initiating ATM transactions, including cashwithdrawals or the like.

A number of terms are used herein for convenience and ease ofexposition. For example, the term “capture” will be used to refer to theact of scanning, reading or other capturing of an “ATM code” or “ATMtoken” (an identifier used to identify specific transactions conductedat ATM devices or to otherwise facilitate a transaction at an ATM devicepursuant to some embodiments). The term “capturing” (or “captured”) isnot intended to be limiting, and is intended to encompass embodimentswhere a mobile device is operated to receive an ATM code (or dataassociated with an ATM code) via key entry, via image capture, via RFIDreading, and using other scanning, reading, or other techniquesdescribed herein. Pursuant to some embodiments, the term “capture”further includes any decoding or image processing of an ATM coderequired to retrieve or otherwise obtain information from the ATM code.

As another example, the term “wireless” is used to refer to unwiredremote communication techniques, such as, for example, using radiofrequency or other electromagnetic radiation based communicationtechniques (including RFID, NFC, wifi, Bluetooth, zigbee or othertechniques). Those skilled in the art, upon reading this disclosure,will appreciate that the use of these terms is not intended to belimiting, but for the purposes of exposition.

Prior to discussing details of certain embodiments, an illustrative (butnot limiting) example of a transaction using features of the presentinvention will first be presented. In the illustrative example, acustomer has an iPhone®. She has installed an ATM transactionapplication (which is configured pursuant to the present invention) ontoher iPhone. The ATM transaction application allows her to use her iPhoneat certain ATM devices to conduct ATM transactions. She wants towithdraw $100 from her checking account, and approaches an ATM devicethat participates in the system of the present invention. At the ATM,she interacts with the ATM display to select an option to “Conduct aMobile Transaction”. This causes the ATM device to send a message to atransaction management system notifying the system that a transaction isto be conducted at that ATM device. The transaction management systemcreates an “ATM code” to be displayed at the ATM device. She then usesher iPhone to capture the code from the ATM device. The captured ATMcode and transaction details are transmitted from the iPhone to thetransaction management system, and the transaction management systemvalidates the transaction and transmits instructions to the ATM deviceto dispense the funds.

In this manner, embodiments allow customers to initiate and conduct awide variety of transactions at ATM devices without need to insert atraditional payment card (such as a debit card or the like) at the ATMdevice. As will be discussed further herein, the use of a mobile deviceallows greater flexibility and control of the transaction, and usersenjoy a number of advantages, including, for example, the ability toaccess a wide variety of accounts (without carrying plastic cards foreach account), and the ability to apply preferences and othertransaction rules. Other advantages will become apparent upon readingthe following disclosure. Further, pursuant to some embodiments, the ATMtransaction application described herein may be integrated with themobile payment applications described in our co-pending and commonlyassigned U.S. patent application Ser. No. 12/846,911 so that mobiledevices may be used to both conduct ATM transactions as well as toconduct purchase transactions at a wide variety of merchants.

System Overview

Features of some embodiments of the present invention will now bedescribed by reference to FIG. 1, which is a block diagram of a system100 pursuant to some embodiments. As shown, a payment account holder, orother user or operator (hereafter, the “customer” or “account holder”)may have or use a mobile device 102 (such as a mobile telephone or thelike). The mobile device 102 has a display screen 136 and a data entrydevice 138 (such as a keypad or touch screen). Pursuant to embodimentsof the present invention, the customer may use the mobile device 102 toconduct ATM transactions with an ATM device 108 by interacting with theATM device 108 and by interacting with an ATM application on the mobiledevice 102. No plastic card (such as a debit card, ATM card or otherbank card) need be inserted into the ATM device 108, instead, thetransaction occurs without the presentation or insertion of a plasticcard into the ATM device 108. The ATM device 108 may be a traditionalATM device (such as an ATM manufactured by Diebold® or the like) orother cash dispensing apparatus, such as an unattended kiosk, or thelike.

In a typical example transaction, a customer (who has an ATM applicationpursuant to the present invention installed on or accessible to theirmobile device 102) approaches an ATM device 108. The customer mayauthenticate themselves to an ATM application on the mobile device 102and then operate the mobile device 102 and the ATM application to causea token or code associated with the ATM device 108 and the currenttransaction to be scanned (shown as interaction 112 in FIG. 1).Alternatively, the customer may authenticate themselves to the ATMapplication after scanning the ATM token or code from the ATM device108. Further details of the authentication and transaction process willbe described further below. In general, however, the customerauthenticates themselves as the legitimate user of the mobile device 102(and the ATM application thereon) to a remote transaction managementsystem 130, and identifies which ATM device the customer wishes totransact with, and in some embodiments, which transaction is to becompleted, by capturing a token or code associated with the ATM device.

In situations where the customer authenticates themselves to the ATMapplication first (before scanning the ATM code), the customerauthentication information (such as a passcode or PIN) are transmittedfrom the mobile device 102 to a transaction management system 130 over acommunication path 114 (e.g., via a wireless or cellular network).

In some embodiments, the customer may authenticate themselves byentering information into the ATM device (either before or after the ATMcode is scanned). Again, these variations will be described furtherbelow.

After the authentication process, and after an ATM code has been scannedfrom the ATM device, data from the ATM code is transmitted from themobile device 102 to the remote transaction management system 130 sothat the transaction management system 130 may identify the specifictransaction the mobile device 102 is involved in as well as theparticular ATM device 108 that the customer wishes to interact with.This may be performed, for example, by matching the ATM code captured bythe mobile device 102 with the corresponding code information at thetransaction management system 130 (which may be, for example, stored ina record of a pending transaction table of a database at the system 130which was generated when the ATM device 108 informed the system 130 ofthe start of the transaction). In this way, the mobile device 102, theATM device 108 and the transaction are matched. Once this matching hasbeen performed, a response message may be returned to the mobile device102 prompting the customer to perform a next step in the transaction. Insome embodiments, the transaction management system 130 may alsotransmit data to the ATM device 108 to facilitate a transactioninvolving the mobile device 102. For example, the transaction managementsystem 130, interacting with either the mobile device 102 or the ATMdevice 108 (or a combination thereof), may cause a display to bepresented to the customer presenting the customer with transactionoptions available (such as, withdraw funds, make a balance inquiry, makea funds transfer, transfer funds to another account holder, etc.). Thedisplay may be displayed on either the ATM device 108 or the mobiledevice 102. The customer then follows the prompts and completes thedesired transaction.

In this manner, embodiments allow customers operating mobile devices tointeract with ATM devices in a way which allows the customer to performtransactions (such as cash withdrawals) to be made at ATM machines. Thisallows customers to reduce the number and type of credit and debit cardsthey carry, and, instead, perform a wide variety of common transactionsusing a mobile device such as a mobile telephone or the like.

A number of techniques may be used to generate or present the ATM code.Pursuant to some embodiments, the ATM code is dynamically generated foreach ATM transaction (or for each ATM device location). In someembodiments, the ATM code is a static identifier associated with anindividual ATM device 108 location. In some embodiments, whether the ATMcode is static or dynamically generated, the ATM code may be displayedon a display device of the ATM device 108 (or on a display associatedwith the ATM device 108).

From the customer perspective, the ATM transaction process of thepresent invention may begin with the customer performing anauthentication process to confirm their identity and authority toconduct ATM transactions using the present invention. The authenticationprocess may be performed after, or in some situations, prior to thecustomer's scanning of an ATM code at a desired ATM device 108. Pursuantto some embodiments, the authentication process serves to authenticatethe customer to the transaction management system 130. Theauthentication process may involve the customer launching a mobile ATMapplication or a Web browser on the mobile device 102 and providing oneor more credentials or items of information to the transactionmanagement system 130 via communication path 114. For example, theauthentication process may involve the entry of a user identifier, apassword, or other credentials into a login screen or other userinterface displayed on a display device 136 of the mobile device 102.The transaction management system 130 compares the received informationwith stored information to authenticate the customer.

The authentication process, in some embodiments, also involves thecomparison of one or more attributes of the mobile device 102 with astored set of attributes collected from the mobile device 102 during aregistration process (where attributes associated with a particularmobile device are linked to a record associated with the consumer). Forexample, the attributes may include identifiers associated with themobile device 102 which uniquely identify the device. In this way, thecustomer is authenticated two ways—with something they know (logincredentials), and something they have (mobile device). Once the customeris successfully authenticated, then the system has access to a varietyof attributes about the customer, including a list of payment accountsthat the customer previously identified to the transaction managementsystem 130 as part of the registration process.

After (or, in some embodiments, before) a successful authenticationprocess, the customer is prompted to scan, capture (or otherwise enter)the ATM code from an ATM device 108 (shown as interaction 112 betweenthe mobile device 102 and the ATM device 108). The ATM code is used, asdescribed further herein, to uniquely identify a specific transactioninvolving a specific ATM device 108, so that transactions pursuant tothe present invention may be accomplished. After capture of the ATMcode, the mobile device 102 transmits the ATM code to the transactionmanagement system 130.

The transaction management system 130, upon receipt of the ATM code fromthe mobile device 102, performs a lookup to uniquely identify thecurrent transaction and the specific ATM device 108 and to confirm thatthe transaction can occur between the customer and the ATM device 108.If the current transaction and the specific ATM device 108 areidentified, a response message is transmitted to the mobile device 102with instructions prompting the customer to take a next step (which mayinclude further interaction with the mobile device 102 or ATM device 108to select further transaction options).

Pursuant to some embodiments, the mobile device 102 may be a smart phoneor a Web enabled mobile device such as, for example, an iPhone®, anAndroid® phone, or any phone that can access and display Web content oraccess the Internet. In some embodiments, the mobile device 102communicates with transaction management system 130 using a cellular orwireless network. In some embodiments, the transaction management system130 is a secure server (or network of servers). In some embodiments, thetransaction management system 130 is in communication with one or moretransaction processing networks (not shown in FIG. 1) such as the STAR®network operated by First Data Resources, the VISANET® network operatedby Visa Inc., the BANKNET® network operated by MasterCard International,or the like. The transaction management system 130 may also be incommunication with other financial transaction networks (such as ACH andEFT networks, private label networks, alternative payment systems suchas PayPal®, or the like) to allow customers operating mobile devices 102to conduct transactions using a wide variety of different forms ofpayment instruments and accounts. The transaction management system 130may further be in communication with one or more ad or offer managementnetworks, such as those provided by Google®, Apple®, Yahoo®, Microsoft®or the like. As will be described further below, data, includingadvertisements and offers may be received from those networks andpresented to customers via the mobile device 102.

Although the system depicted in FIG. 1 (and elsewhere throughout thisdisclosure) shows only a single mobile device 102, ATM device 108 andtransaction management system 130, those skilled in the art willappreciate that in use there will be a number of devices in use, anumber of ATM systems and devices and networks using the system, andpotentially multiple instances of the transaction management system inoperation.

Further System Details

Further details of some aspects of a system according to someembodiments of the present invention will now be described by referenceto FIG. 2. FIG. 2 is a block diagram of an example payment systemnetwork environment showing communication paths between a mobile device202, ATM devices 208, transaction management system 230 and paymentprocessing systems 232. Mobile device 202 may be, for example, a mobiletelephone, PDA, personal computer, or the like. For example, mobiledevice 202 may be an iPhone® from Apple, Inc., a BlackBerry® from RIM, amobile phone using the Google Android® operating system, or the like.Pursuant to some embodiments, mobile device 202 may operate an ATMapplication allowing mobile device 202 to operate as a payment device asdescribed herein. In some embodiments, mobile device 202 is capable ofaccessing and displaying Web content or otherwise accessing the Internetso that a customer operating mobile device 202 may interact withtransaction management system 230 to initiate a transaction via a Webinterface.

Mobile device 202 of FIG. 2 can, for example, communicate over one ormore wired and/or wireless networks 201. As an example, a wirelessnetwork can be a cellular network (represented by a cell transmitter215). A mobile device 202 may communicate over a cellular or otherwireless network and through a gateway 216 and then communicate with anetwork 214 (e.g., such as the Internet or other public or privatenetwork). An access point, such as access point 218 may be provided tofacilitate data and other communication access to network 214. Accesspoint 218 may be, for example, compliant with the 802.11g (or other)communication standards. For example, in embodiments in which a mobiledevice 202 is operating an ATM application which allows mobile device202 to function as a payment device pursuant to the invention, the ATMapplication may cause or control communication of data through network201 to transaction management system 230.

In some embodiments, mobile device 202 may engage in both voice and datacommunications over wireless network 214 via access point 218. Forexample, mobile device 202 may be able to place or receive phone calls,send and receive emails, send and receive short message service (“SMS”)messages, send and receive email messages, access electronic documents,send and receive streaming media, or the like, over the wireless networkthrough access point 218. Similar communications may be made via network215.

In some embodiments, a mobile device 202 may also establishcommunication by other means, such as, for example, wired connectionswith networks, peer-to-peer communication with other devices (e.g.,using Bluetooth networking or the like), etc. Mobile device 202 can, forexample, communicate with one or more services over networks 201, suchas the transaction management system 230 (to conduct paymenttransactions, to create, edit, view or otherwise modify payment accountsettings and preferences, etc.), the Web 240, and other services 242.Mobile device 202 can also access other data over the one or more wiredand/or wireless networks 201. For example, content providers, such asnews sites, RSS feeds, web sites, blogs, social networking sites,developer networks, etc., can be accessed by mobile device 202. Suchaccess can be provided by invocation of a web browsing function orapplication (e.g., a browser) in response to a customer launching a Webbrowser application installed on mobile device 202. In some embodiments,a user may utilize a Web browser to interact with transaction managementsystem 230 to register transaction accounts, establish accountpreferences, perform ATM or other financial transactions, etc.

Mobile device 202 has a display screen 236 and a data entry device 238(such as a keypad or touch screen, or voice interface). Pursuant toembodiments of the present invention, the customer may use the mobiledevice 202 to conduct ATM transactions with one or more ATM devices 208.ATM devices 208 may be traditional ATMs or other kiosks or cashdispensing devices. Mobile device 202, in some embodiments, also has acamera (not shown) or other image capture device which allows the mobiledevice 202 to capture an image or representation of an ATM token 210associated with an ATM device 208. Mobile device 202, in someembodiments, also has a wireless receiver (not shown) or other wirelesssignal receiving device which allows the mobile device 202 to capture awireless signal representation of an ATM token 210. For example, acustomer may operate mobile device 202 to take a digital picture orcapture the image of an ATM code 210 displayed on or at an ATM device208 to initiate an ATM transaction using the present invention. Thecaptured image is shown as item 237 on the display screen 236. As willbe described further below, the ATM code 210 may be used to initiate andconduct transactions with an ATM device (as well as to conducttransactions with merchants pursuant to the disclosure of our co-pendingapplication Ser. No. 12/846,911).

Pursuant to embodiments of the present invention, an ATM code 210 isdisplayed on or near a display device 212 of an ATM device 208 point ofsale. The ATM code 210 may be either a “static” ATM code or a “dynamic”ATM code. In situations where static ATM codes are used, the ATM codemay be printed, displayed, or provided near the ATM device (such as on asticker or placard displayed so the customer can easily see and read orcapture the ATM token). Static ATM codes 210 may be printed as a barcode image, as an alphanumeric identifier, or in other forms. In someembodiments, ATM codes may be presented in forms which are easilydiscernable by a human so that they may be both key-entered or capturedusing a mobile device 202.

In embodiments where dynamic ATM codes are used, the ATM code may bedisplayed on a display device 213 associated with an ATM device 208. Adynamic ATM code may be generated to uniquely identify a specifictransaction involving an ATM device, and may be “dynamic” in that theATM code information changes from transaction to transaction (e.g., theATM code may be randomly generated for each transaction, or may be basedon a time stamp as well as the location of the ATM device, transactiondetails, or the like). In some embodiments, the dynamic code includesinformation about a specific transaction (which may be generated basedon information entered by the customer either at the mobile device 202or at the ATM device 208 when the transaction is initiated). Forexample, the code may encode or include information identifying atransaction type (deposit, withdrawal, funds transfer, person to persontransfer, etc.) and/or a transaction amount. In some embodiments, thedynamic code may also encode or include information associated withadditional information helpful or related to the transaction orspecifying one or more targeted offers or messages (such as by includingan informational or messaging URL or the like). In some embodiments,where transaction information is encoded in the code 210, when themobile device 202 is subsequently operated to scan or capture the ATMcode 210, the mobile device may decode some or all of the information tospeed the transaction process (e.g., to identify or confirm thetransaction type or amount).

A transaction at an ATM device 208 may proceed in several ways pursuantto various embodiments of the present invention. For example, in oneembodiment, the transaction starts at the ATM device 208 with a customerselecting an option to initiate a mobile transaction, which causes anATM code to be displayed on a display device of the ATM device 208 forcapture by the mobile device 202. Information associated with the ATMcode, as well as additional information may be transmitted to atransaction management system 230 for processing. For example,information may be transmitted from the mobile device 202 to atransaction management system 230 to verify a device signature of themobile device. The device signature may be a unique combination ofhardware attributes selected to verify the mobile device's signature toverify that the device was known or recognized by the system 230. If thedevice signature is not recognized, the ATM transaction process may notproceed. The customer is then prompted to enter “something they know”such as a user identifier and password or PIN (or other usercredentials). This information would be used to verify that the user hasa valid account on the system 230. In some embodiments, the informationmay be entered into the mobile device 202, while in other embodimentsthe information may be entered into the ATM device 208.

Once the user has been successfully authenticated, the system 230 wouldthen take the additional step of verifying that the device signature ofthe mobile device 202 was associated with the user credentials that hadbeen entered. If the association was valid, the customer could continuethe ATM transaction. If not, the ATM transaction would be ended by thesystem 230.

In this way, the customer would have identified themselves as anauthorized user of the network (and participant in the system 230) byusing something they have (their specific mobile device 202) andsomething they know (such as their user identifier and password or othercredentials).

In some embodiments, the customer is prompted to (and does) scan the ATMcode 210 prior to the authentication processing. In other embodiments,the customer may be prompted to perform the authentication processingfirst, and then is prompted to (and does) scan a ATM code 210 displayedon the ATM device 208 to indicate which specific ATM device 208 theywish to transact with (e.g., to receive cash from).

Regardless of whether the code is scanned before or afterauthentication, the ATM code may be a either a static or a dynamic code.A “dynamic” ATM code 210 may be a visual code generated for eachtransaction, and may be displayed as a barcode (or other image) on adisplay device 212 associated with the ATM device 208. In someembodiments, the ATM code 210 may be a static visual ATM code such as abarcode that is fixed (and uniquely associated with a specific ATMdevice 208). In some embodiments, the ATM code 210 is a static ordynamic ATM code in an RFID or NFC chip that can be read by a mobiledevice 202 with an NFC or RFID reader.

Once authentication of the customer and the mobile device 202 iscomplete, and the ATM code 210 has been scanned and transmitted to thetransaction management system 230, the customer may be presented with auser interface and transaction options in several different ways. Forexample, the user interface (which may provide options such as “getbalance”, “make withdrawal”, “make transfer”, etc) may be displayed on adisplay screen 236 of the mobile device 202 (and the selections may becommunicated to the transaction management system 230 through network201, and then relayed to the ATM device 208 through network 220). Asanother example, the user interface may be displayed on a display screen212 of the ATM device 208 (and the customer's selections may becommunicated to the transaction management system 230 through network220).

Once the instructions have been confirmed and passed to the ATM device208, the ATM device may be operated to perform any required actions(such as to dispense a certain amount of currency, display a balance,print a receipt, etc.). The reconciliation from the customer's accountis performed under control of the transaction management system 230(e.g., to cause an amount of funds to be debited from a selectedaccount, or the like).

In some embodiments, the mobile device 202 implements the same derivedunique key per transaction encryption scheme as used on the ATM device208 which, in effect, turns the mobile device in to an ATM device withthe same encryption scheme. For example, the mobile device 202 may actas a hardware security module to generate encryption keys in a tamperproof manner. The derived unique keys may be used to encrypt data sentto and from the mobile device 202 in the same manner as if the data wassent from the actual ATM device 208.

In an alternative embodiment, an ATM transaction proceeds as follows.First, the customer launches an ATM application on their mobile device202, and the transaction management system 230 verifies the “devicesignature” of the mobile device (a unique combination of device hardwareattributes) to verify the mobile device's signature with a set of knownsignatures to verify that the mobile device was “known” to the system230. If the mobile device signature was not recognized, the customercould not proceed further in the authentication process.

Next, the customer scans an ATM code 210 displayed on the ATM device208. The ATM code 210 that is scanned is sent by the mobile device 202to the transaction management system 230, which then compares thereceived ATM code 210 to determine: (i) if the ATM code 210 is a validATM code issued by the system 230 (and, in some embodiments, matches atransaction record created when a dynamic code was generated for the ATMdevice), (ii) the location of the ATM device 208 that the ATM code 210was allocated or associated with, and/or (iii) transaction details (suchas the type of transaction, the transaction amount, etc.). As discussedabove, the ATM code 210 may be static or dynamic.

The customer is then prompted to enter “something they know” such as auser identifier and password or PIN (or other user credentials). Thisinformation would be used to verify that the customer has a validaccount on the system 230. The information may be entered into themobile device 202 or into the ATM device 208.

Once successfully authenticated, the system 230 would then take theadditional step of verifying that the device signature of the mobiledevice 202 was associated with the user credentials that had beenentered. If the association was valid, the customer could continue thesession. If not, the session would be ended by the system 230. In thisway, the customer would have identified themselves as an authorized userof the system 230 by using something they have (their mobile device 202)and something they know (userid and password or other credentials).

Once authentication of the customer and the mobile device 202 iscomplete, the customer may be presented with a user interface andtransaction options in several different ways. For example, the userinterface (which may provide options such as “get balance”, “makewithdrawal”, “make transfer”, etc) may be displayed on a display screen236 of the mobile device 202 (and the selections may be communicated tothe transaction management system 230 through network 201, and thenrelayed to the ATM device 208 through network 220). As another example,the user interface may be displayed on a display screen 212 of the ATMdevice 208 (and the customer's selections may be communicated to thetransaction management system 230 through network 220).

Once the instructions have been confirmed and passed to the ATM device208, the ATM device may be operated to perform any required actions(such as to dispense a certain amount of currency, display a balance,print a receipt, etc.). The reconciliation from the customer's accountis performed under control of the transaction management system 230(e.g., to cause an amount of funds to be debited from a selectedaccount, or the like).

User Interface Examples

Reference is now made to FIG. 3 which depict an illustrative userinterface that may be presented to a user operating a mobile device(such as the mobile device 202 of FIG. 2) on a display screen of thedevice (such as the display 236 of FIG. 2) so that the customer canconduct ATM transactions using features of embodiments of the presentinvention. The customer interface is shown as being displayed on anApple iPhone mobile device—those skilled in the art will appreciate thatsimilar user interfaces may be displayed on other mobile devices.

A mobile device 302 is shown which has a display 336 showing an image ofan ATM code (represented as a dynamic two dimensional bar code image or“QR code” 337) which has been captured or imaged by a camera associatedwith the mobile device 302. The ATM code has been captured by a customeroperating the mobile device 302 during the course of an ATM transactionusing embodiments of the present invention (e.g., the display shown inFIG. 3 may have been captured during the transaction processingdescribed herein). In some embodiments, the mobile ATM applicationrunning on the mobile device 302 is configured to automatically capture,decode, and transmit the code during the course of an ATM transaction.While the code is shown as being an encoded two dimensional bar codeimage, those skilled in the art will appreciate that it may be displayedin any of a number of different formats, such as, for example, a 1dimensional barcode format such as a UPC, code 39, EAN 8 or EAN 13,other two dimensional formats such as PDF 417 or Datamatrix, other ndimensional barcode formats, or alphanumeric text or symbols or thelike.

The display of the mobile device 302 also includes a number of buttonsor icons 340, 342 which allow the customer to perform functionsassociated with the payment system of the present invention. Forexample, as depicted, the customer may choose to reset 340 the capturingof the ATM code (e.g., in the event that the code was not properlycaptured or read) or the customer may select among other choices. Insome embodiments, the selection or specification of transaction detailsmay, instead, be displayed on a display screen of the ATM device 208.

Those skilled in the art will appreciate that other user interfaces,messages and screens may be used to present payment options, transactioninformation and other details to a user of a mobile ATM applicationpursuant to the present invention.

For example, as shown in FIGS. 4A-4B, a further user interface 420 maybe displayed after the customer launches an ATM payment applicationpursuant to the present invention. The user interface 420 may bedisplayed before or after the ATM code has been captured. An embodimentwhere the user interface 420 is displayed after an ATM code has beencaptured is shown in FIG. 4A. As depicted, the user interface 420displays information confirming the transaction details and informationentered by the account holder at the ATM device. In some embodiments,this information may be obtained by the mobile device 202 frominformation associated with the ATM code captured by the mobile device202. In some embodiments, as depicted in the embodiment illustrated inFIG. 4B, transaction options may be selected by the account holder onthe mobile device 202 prior to the time the ATM code is captured. Forexample, as shown in FIG. 4B, the user interface 420 provides a numberof options associated with a default transaction account previouslyspecified by the customer. Those skilled in the art will appreciate thatadditional or different options may be presented. Further, some or allof the options may instead, or in addition, be displayed to the customeron a display device of the ATM device 208.

As shown in FIGS. 5A-5B, a further user interface 520 may be displayedto the customer providing instructions on how to complete thetransaction at the selected ATM device 208. In some embodiments, theuser interface 520 instructs the customer to interact with the ATMdevice 208 to finalize the transaction. For example, the customer may beinstructed to press a button or make a selection on a display screen orkeypad of the ATM device 208 (such as “next” or the like). Since thetransaction management system 230 has been in communication with the ATMdevice 208, instructions authorizing the ATM device 208 to complete thetransaction will have been sent, and the customer can complete thetransaction.

In some embodiments, to provide an additional step to confirm thecustomer is authorized to complete the transaction with the ATM device208, a further step such as shown in the user interface 520 of FIG. 5Bmay be used. In the illustrated example, a shared secret (such as apasscode or the like) may be transmitted to both the mobile device 202and to the ATM device 208 to allow the customer to complete therequested transaction. Those skilled in the art, upon reading thisdisclosure, will appreciate that other interactions or messages may bepresented to the customer providing instructions on how the transactionat the ATM device 208 is to be completed.

As shown in FIG. 6, a confirmation screen may be displayed to thecustomer at the end of the requested transaction. In some embodiments,the customer may be presented with additional options associated withthe transaction.

Mobile Device

Reference is now made to FIG. 7, where a block diagram is showndepicting components of a mobile device 700 pursuant to someembodiments. As depicted, the mobile device 700 includes a number ofcomponents which may be controlled or perform functions in conjunctionwith one more application programs 710-712 to perform the features ofsome embodiments.

The mobile device 700 can include a memory interface 702 one or moredata processors, image processors and/or central processing units 704,and a peripherals interface 706. The memory interface 702, the one ormore processors 704 and/or the peripherals interface 706 can be separatecomponents or can be integrated in one or more integrated circuits. Thevarious components in the mobile device 700 can be coupled by one ormore communication buses or signal lines.

Sensors, devices and subsystems can be coupled to the peripheralsinterface 706 to facilitate multiple functionalities. For example, oneor more sensors, including a biometrics sensor 714, an accelerometer716, a photoelectric device 718, a proximity sensor 720, a camera 722, awireless communication unit 724, an audio unit 726 and a magnetometer728 may be provided to facilitate the collection, use and interactionwith data and information and to achieve the functions of the paymentapplications described herein. For example, when provided, themagnetometer 728 may be used to calculate a position of the mobiledevice 700 in space, allowing improved capturing of ATM codes.

The mobile device 700 may include one or more input/output (I/O) devices730 and/or sensor devices. For example, input controllers 734 may beprovided with a speaker and a microphone (not shown) to facilitatevoice-enabled functionalities, such as phone and voice mail functions.In some implementations, a loud speaker can be included to facilitatehands-free voice functionalities, such as speaker phone functions. Anaudio jack can also be included for use of headphones and/or amicrophone.

The I/O subsystem 730 can include a touch screen controller 732 and/orother input controller(s) 734. The touch-screen controller 732 can becoupled to a touch screen 736. The touch screen 736 and touch screencontroller 732 can, for example, detect contact and movement or breakthereof using any of a plurality of touch sensitivity technologies,including but not limited to capacitive, resistive, infrared, andsurface acoustic wave technologies, as well as other proximity sensorarrays or other elements for determining one or more points of contactwith the touch screen 736.

The other input controller(s) 734 can be coupled to other input/controldevices 738, such as one or more buttons, rocker switches, thumb-wheel,infrared port, USB port, and/or a pointer device such as a stylus. Theone or more buttons (not shown) can include an up/down button for volumecontrol of the speaker and/or the microphone.

In some implementations, a proximity sensor 720 can be included tofacilitate the detection of the account holder positioning the mobiledevice 700 proximate to an ATM, a display associated with the ATM, or asticker or other indicator associated with a specific ATM location and,in response, to activate the camera or other reader to detect or capturean image of an ATM code.

Other sensors can also be used. For example, in some implementations, aphotoelectric device 718 may be provided to facilitate adjusting thebrightness of the touch-screen display 738. In some implementations, anaccelerometer 716 can be utilized to detect movement of the mobiledevice 700, and a magnetometer can also be used to help detect theposition of the mobile device. In some embodiments, the mobile device700 may include circuitry and sensors for supporting a locationdetermining capability, such as that provided by the global positioningsystem (GPS) or other positioning system (e.g., systems using Wi-Fiaccess points, television signals, cellular grids, cellular towers, orUniform Resource Locators (URLs)). In some implementations, apositioning system (e.g., a GPS receiver) can be integrated into themobile device 700 or provided as a separate device that can be coupledto the mobile device 700 through a peripherals interface 706 to provideaccess to location-based services. The positioning and location-basedservices may be used, for example, to tag data transmitted from themobile device 700 to transaction management systems. For example, suchlocation data may be used to further identify a specific ATM which thecustomer is interacting with during an ATM transaction, and may also beused to assist in fraud detection by insuring that the mobile device isin close proximity to the ATM location specified in the informationreceived in or derived from a transaction request.

The mobile device 700 can also include a camera lens and sensor 722. Insome implementations, the camera lens and sensor 722 can be located onthe back surface of the mobile device 700, or on the front surface. Thecamera can capture still images and/or video. The camera may be used,for example, to capture or capture images of an ATM code associated witha specific ATM to be used by the account holder. In some embodiments,the operation of the camera 722 may be controlled by a transactionapplication installed on the mobile device 700. As a specific example,when the transaction application is activated to conduct an ATMtransaction, the camera 722 may be placed in a ready mode of operationso that as soon as the camera lens and sensor 722 are placed proximateto an ATM code, the camera lens and sensor 722 may be operated tocapture an image of the ATM code for use in the ATM transactionapplication.

The mobile device 700 can also include one or more wirelesscommunication subsystems 724, such as an 802.11b/g communication device,RFID, NFC, and/or a Bluetooth® communication device. Other communicationprotocols can also be supported, including other 802.x communicationprotocols (e.g., WiMax, Wi-Fi), code division multiple access (CDMA),global system for mobile communications (GSM), Enhanced Data GSMEnvironment (EDGE), 3G (e.g., EV-DO, UMTS, HSDPA,), 4G, LTE, etc.

In some implementations, additional sensors or subsystems may be coupledto the peripherals interface 706 via connectors such as, for example aUniversal Serial Bus (USB) port, or a docking port, or some other wiredport connection.

The memory interface 702 can be coupled to memory 708. The memory 708can include high-speed random access memory and/or non-volatile memory,such as one or more magnetic disk storage devices, one or more opticalstorage devices, and/or flash memory (e.g., NAND, NOR). The memory 708can store an operating system, such as Android, IOS from Apple, Darwin,RTXC, LINUX, UNIX, OS X, WINDOWS, or an embedded operating system suchas VxWorks. The operating system may include instructions for handlingbasic system services and for performing hardware dependent tasks. Insome implementations, the operating system can be a kernel (e.g., UNIXkernel).

The memory 708 may also store application programs 710-712 which act, inconjunction with the processors 704, to cause the mobile device tooperate to perform certain functions, including the ATM transactionapplication related functions described herein.

The memory 708 can also store data, including but not limited todocuments, images (including images containing advertisements andoffers), video files, audio files, and other data. The mobile device 700may be configured to operate using a number of different operatingsystems and to communicate using a number of different communicationsnetworks. Those skilled in the art will appreciate that the mobiledevice 700 may be sized as a handheld mobile phone, or other portabledevice such as a tablet computer or the like.

Transaction Process

Reference is now made to FIG. 8, which is a flow diagram illustrating atransaction process 800 pursuant to some embodiments. The process 800 isshown from the perspective of an account holder (or “customer”)operating a mobile device. For example, transaction process 800 includesa number of steps that may be performed by a customer operating a mobiledevice (such as the device 202 of FIG. 2) to complete transactions atATMs pursuant to the present invention. Pursuant to some embodiments,the process 800 is executed under control of application softwareinstalled on the mobile device 202. In other embodiments, the process800 is executed under control of software maintained and operated at aremote transaction system (or Web server in communication with thetransaction system) and the mobile device 202 interacts with thesoftware via a Web browser. The use of an application program will bedescribed herein.

In some embodiments prior to executing an ATM transaction using themobile device 202, a customer may first perform a registration processin which data associated with transaction accounts (such as one or morechecking, savings, or other ATM-accessible accounts) are provided to thetransaction management system and associated with the ATM application.Further, in some embodiments, authentication data for use inauthenticating the customer and the mobile device 202 during atransaction may also be identified. Registration may include customerinteraction with a registration server (which may be a component of, orrelated to, transaction management system 230 of FIG. 2) to initiate aregistration process. For example, the customer may operate an Internetbrowser (either on a mobile device or another computing device) toaccess a registration Web page associated with the registration server.The registration Web page may request the customer provide someidentifying information to begin the account creation process. Forexample, a customer may provide name, address and other contactinformation as well as contact preferences, including one or more emailaddresses and phone numbers. The customer may also establish an accountduring the registration process. The account may be associated withcontact and identifying information associated with the customer, aswell as information identifying one or more mobile device(s) from whichthe customer wishes to conduct ATM transactions. Each mobile device 202may, for example, be identified by its phone number and/or other uniqueidentifier(s) (such as a hardware serial number, an ASIN, a UUID in thecase of an iPhone, a component serial number such as a CPU serial numberor the like). In some embodiments, where the customer registers from abrowser on their mobile device, or by first downloading an ATMapplication having a registration module onto their mobile device, thesystem may capture unique identifying information associated with themobile device (e.g., such as a hardware serial number, an ASIN, a UUIDor other device identifiers).

During the registration and account set up, the customer also providesinformation about one or more transaction accounts that the customerwishes to have associated with the ATM transaction system of the presentinvention. For example, the customer may enter information about one ormore bank accounts, checking accounts, savings accounts, or the like.The information about each account includes the actual paymentcredentials or sufficient information to process a transaction using theaccount. For example, with respect to a bank account, the informationmay include: the routing number and the account number. Information froma debit card or ATM card may also be provided (including a primaryaccount number, expiry date, and data typically associated with Track 1and/or Track II of a magnetic stripe of a card). Some or all of thisdata may be obtained by transaction management system 230 directly fromthe financial institution associated with the transaction account (withauthorization from the account holder).

In some embodiments, the customer may optionally establish one or morepreferences or rules associated with the use of one or more of thetransaction accounts. For example, the customer may designate one of theaccounts as the “primary” or default account. Other rules andpreferences may also be set to enable accounts to be selected and usedin an efficient and logical manner. For example, a customer may specifypriorities or other account-based rules to indicate which transactionaccount is the default account for cash withdrawals, which one is thedefault for deposits, and which one should be used for overseas ATMtransactions.

A customer may also specify transaction limitations or balancerequirements that govern how and when a transaction account is to bepresented as an option. For example, if a customer's Bank of Americachecking account allows 2 free ATM withdrawals each month, and thecustomer's JP Morgan Chase savings account also allows 2 free ATMwithdrawals a month, the customer may wish to use the Bank of Americaaccount 2 times and the Chase account 2 times (subject to other balancerules and preferences set by the customer).

In some embodiments, a rule (such as a customer-specified rule), maycause a payment process to proceed more quickly, or with fewer customersteps. For example, a customer may specify that when conducting atransaction at an ATM, she typically wishes to withdraw a default amountof cash each time, and typically wishes to use her default checkingaccount. In such situations, an ATM transaction using the presentinvention may proceed without need for the customer to select or confirmthe selection of the transaction account and transaction details—it isdone automatically by application of the customer-specified rule.

Those skilled in the art will appreciate, upon reading this disclosure,that a wide variety and type of account-level rules may be specified toallow a customer to manage how (and when) transaction accounts arepresented as transaction options.

Referring again to the process 800 of FIG. 8, once a customer hasregistered and configured an account and a transaction applicationpursuant to the present invention, she may use the mobile device 202 toconduct an ATM transaction at participating ATM devices 208. Process 800begins at 802 where the customer who is a participant in the ATMtransaction program of the present invention launches an ATM applicationon their mobile device 202. The ATM transaction application may be an“app” or computer program code stored on the mobile device 202, or, insome embodiments, the ATM transaction application may be accessed bypointing a Web browser associated with the mobile device 202 to a Webpage associated with an ATM application over the Internet. For theremainder of this discussion of process 802, it will be assumed that theATM transaction application is an application stored on the mobiledevice 202 (but such discussion is not intended to limit the applicationof the present invention to such an embodiment). In some embodiments,the start of a transaction may also include the customer selecting anoption to perform a mobile transaction at an ATM device 208 (which, asdiscussed above, may cause a message to be transmitted to a transactionmanagement system which generates an ATM code for display on a displayscreen of the ATM device 208 for capture by the customer).

Processing continues at 804 where the customer is prompted to enterauthentication information. For example, the customer may be prompted toenter information such as a user identifier, a password, or othercredentials into a login screen displayed on the mobile device 202.Processing at 804 may also include collecting or generatingdevice-related information for use in authenticating the customer. Thecustomer authentication information, as well as any device-relatedinformation, are transmitted to the transaction management system 230(e.g., over a network 201) for authentication by the transactionmanagement system 230. In some embodiments, processing at 804 may beperformed subsequent to the capture of an ATM code (described below at810).

A determination is made at 806 whether the authentication passed orfailed (e.g., based on a response received from the transactionmanagement system 230). If the authentication failed, processing maycontinue at 808 where the customer is informed of the failure and iseither prompted to reattempt the authentication process or that thetransaction request has been terminated. The transaction managementsystem 230 uses the received information to determine if the customer(and/or device) can be successfully authenticated based on informationpreviously stored at or accessible to the transaction management system230. For example, in the situation where a password authentication isrequired, processing at 806 may include a determination of whether thepassword received matches a stored password for the customer.

Processing continues at 810 if the authentication processing issuccessful (that is, if the customer and the device have successfullybeen identified by the transaction management system 230), where themobile payment application enables the customer to take steps to capturean ATM code displayed on a display screen of (or otherwise associatedwith) the ATM device 208 the customer wishes to conduct a transactionwith. Processing at 810 may also include presenting a list of ATMtransaction options to the customer. For example, once the ATM code hasbeen captured, the mobile device may display all of the customer'stransaction accounts that have been registered with the system. Thisallows a customer to view their available accounts as well as availabletransaction prior to completing a transaction.

For example, in some embodiments, the customer may be prompted to pointa camera of the mobile device 202 at a bar code image of an ATM code andto operate the mobile device 202 to capture the image. As anotherexample, the customer may be prompted to key enter the ATM code orotherwise enter it into the mobile device 202. In some embodiments, theATM code 210 is captured by a camera or other image capture device ofthe mobile device 202 (e.g., as shown in the user interface diagram 300of FIG. 3). For example, in some embodiments, the ATM transactionapplication on the mobile device 202 is configured to automaticallydetect and capture the ATM code 210 using a camera associated with themobile device 202, or a wireless receiver.

In some embodiments, the camera may be operated in a continuous scanningmode where (without input from the user except, for example, a singlepush of the “Pay” button) the camera will rapidly (multiple times eachsecond) capture an image of the ATM code 210, each of which is processedby the mobile application until it successfully decodes the image of theATM code 210. This continuous scanning mode is useful, since it freesthe user from repeatedly having to push the camera button to captureimages in the case where the first images captured cannot be decoded bythe application, due to, for example, the image not being clear enoughdue to the camera's viewfinder not completely capturing the image of theATM code or for other reasons. To optimize and speed this process, theapplication may take into account specific attributes of the phone andits camera hardware, including the resolution of the image captured, thefocal length of the camera, and other attributes. To further optimizethe capture process, the size of the token, the angle of the surface onwhich the ATM code 210 is displayed, and other information may also beused to optimize the speed and accuracy of the ATM code capture process.

The ATM transaction application installed on the mobile device 202 mayinteract with one or more other sensors (such as those described abovein conjunction with FIG. 7, including, for example, a magnetometer, agyroscope, and/or an accelerometer) during a capture process. In someembodiments, the ATM transaction application may interact with suchsensors to improve capture accuracy. For example, the ATM transactionapplication may adjust characteristics or control of the mobile device'scamera hardware (e.g., such as by adjusting or controlling the imageresolution and/or focal length of the camera), or adjust the algorithmsand processes used to search the image data for a ATM code 210, based ondata received from sensors such as a magnetometer, gyroscope,accelerometer or the like. For example, data associated with a mobiledevice, it's sensors, and hardware characteristics (such as the focallength of the device's camera, the model of the phone, etc.) may be usedas inputs for calculating a camera matrix or a projection matrix whichis used to assist in compensating for image distortions including skewor the like. In this manner, data from mobile device 202 positioning orother characteristics may be taken into account when attempting tocapture ATM codes, thereby ensuring accurate and consistent capture ofdata. Further, this data and these compensation techniques may be usedto more quickly locate an ATM code during an imaging or capture process.

As an illustrative example, referring to an example camera on an iPhonedevice, the projection matrix may be dependent on a few physicalcharacteristics, including the camera focal length (which is 3.85 mm forone version of the phone), the imaging plane (which is ¼″ for the sameversion of the phone), the physical size of the position marks in acapture, and the physical distance between the position marks. Based onthis information, embodiments are able to identify a spatial locationfor position marks relative to the camera, and from that data, a tilt ofthe checkout token relative to the camera sensor may be calculated.Pursuant to some embodiments, a projection matrix (or camera matrix) isused to describe the tilt with respect to the camera sensor and is usedto adjust the capture process to ensure that ATM codes may beefficiently and accurately captured even in situations where thecustomer is not holding the mobile device 202 in a manner where thecamera sensor is directly orthogonal to the ATM code. By improving thecapture process using these techniques, the customer experience andspeed and accuracy of capturing ATM codes is improved.

In embodiments where the ATM code 210 is displayed in the form of anencoded bar code image, the ATM transaction application installed on themobile device 202 may automatically operate to decode the bar code imageto obtain the ATM code 210. The encoded bar code image may be presentedin a number of different formats, including as a one dimensional or twodimensional bar code image or the like. In some embodiments, the ATMcode 210 may be displayed as an unencoded string of characters that maybe key-entered into the payment application of the mobile device. Insome embodiments, the ATM code 210 may be read or entered into thepayment application of the mobile device using other means, such as, forexample, by wireless communication (e.g., such as by Bluetoothcommunication, by RFID detection, by optical character recognition, orthe like).

Processing continues at 812 where the customer specifies one or moretransaction details, including, for example, a transaction type (e.g.,withdrawal, deposit, balance inquiry, etc.) and a transaction amount.This information may be received from the customer via an input deviceof the mobile device 202 (such as illustrated in FIG. 4) or it may beentered by the customer onto a display screen of the ATM device 208. Thecustomer may also specify a desired account with which to conduct thetransaction.

Processing may continue at 814 where the mobile device 202 transmits theATM code and the transaction details in a customer transaction requestmessage to the transaction management system 230. In some embodiments,the customer transaction request message includes information associatedwith the identity of the customer (determined during the authenticationprocess). This information, coupled with information about the mobiledevice 202, allows the transaction management system 230 to determinethat it is interacting with an authorized user operating an authorizeddevice, allowing the system to locate the appropriate transactionaccount(s) for the user. The transaction management system 230 uses theATM code and additional information received from the mobile device 202(e.g., such as location data) to identify the specific transaction, thecustomer, and the specific ATM device 208 (or group of devices) withwhich the customer wishes to conduct a transaction. The ATM device(s)208 may be identified by performing a database lookup of devices. Thetransaction management system 230 may also determine, based on theidentified ATM device 208 or on other information contained within thetransaction request message, a list of possible transaction options andother information for use in responding to the customer transactionrequest message.

In conjunction with processing the customer transaction request message,the transaction management system 230 may interact with the ATM device208 identified by the ATM code 210 to activate it or configure it foruse in completing or conducting the transaction with the customer. Insome embodiments, this may include transmitting information associatedwith the customer and the customer's selected transaction account to theATM device 208, effectively enabling or activating the ATM device 208for use in completing the transaction (e.g., by transmitting data to theATM device 208 through an ATM switch or network). In some embodiments(as shown in conjunction with FIG. 5B, above) some authenticationinformation may also be transmitted to both the ATM device 208 as wellas the mobile device 202 (such as a passcode to be entered by thecustomer to complete the transaction). In some embodiments, thetransaction management system 230 may await further information from thecustomer before transmitting information to the ATM device 208 (e.g.,such as awaiting a transaction amount and transaction type from thecustomer).

Processing continues at 816 where the customer completes thetransaction. Completion of the transaction includes some customerinteraction with the ATM device 208 (e.g., to withdraw cash, depositfunds, or the like). In some embodiments, processing at 816 may includepresenting specific instructions to the customer (e.g., on a displayscreen of the mobile device 202), such as shown in FIG. 5. For example,the transaction management system 230, in response to a customertransaction request, and after authenticating the customer, the mobiledevice, and the received ATM code 210, establishes communication withthe specific ATM device 208 identified by the code 210 and allows thecustomer to conduct the transaction. In some embodiments, this involvestransmitting instructions to the ATM device to activate a cashdispenser, a deposit mechanism, or the like. In other embodiments, thismay include communicating a shared secret (such as a passcode or thelike) to both the mobile device 202 and to the ATM device 208. Thecustomer then causes the shared secret to be entered into the ATM device208 to conduct the transaction.

Once the transaction is complete, processing continues at 818 where atransaction completion message is received. In some embodiments, thetransaction completion message may be displayed on a display device ofthe mobile device 202, confirming to the customer that the transactionhas concluded.

While a number of transaction flows have been described herein, thoseskilled in the art, upon reading this disclosure, will appreciate that anumber of other flows may be achieved using features of the presentinvention. For example, in some embodiments, most of the transactioninteraction and details may be specified by the account holder byinteracting with the mobile device 202 prior to approaching an ATMdevice 208 (such as by completing an authentication process, selecting atransaction type, a transaction amount, and an account). Then, when theaccount holder is ready to conduct the transaction, she can approach theATM device 208, select an ATM option for a “mobile transaction” and scanor capture the ATM code 210 that is presented by the ATM device 208. Thetransaction may then complete with little to no further action by theaccount holder. In this manner, ATM transactions may be completedquickly and efficiently, triggered and completed by the act of capturingthe ATM code. Those skilled in the art will now appreciate that a numberof other transaction processes may be realized using features of thepresent invention.

Further, although traditional ATM-type transactions have been describedherein, embodiments may be used to conduct other types of transactionsas well. For example, embodiments may be used to conduct funds transfersbetween the account holder and remote parties, such as other accountholders or entities. As a specific example, embodiments may be used toconduct person to person fund transfers, including funds transfers wherethe account holder deposits funds into an ATM device, and authorizesthose funds to be transferred to another person.

Although the present invention has been described in connection withspecific exemplary embodiments, it should be understood that variouschanges, substitutions, and alterations apparent to those skilled in theart can be made to the disclosed embodiments without departing from thespirit and scope of the invention as set forth in the appended claims.

I claim:
 1. A method for operating a mobile device to complete atransaction between an account holder and an automated teller machine(“ATM”), the method comprising: causing an ATM code to be captured bythe mobile device, the ATM code presented to the account holder at alocation of said ATM; transmitting, to a remote transaction managementsystem, a transaction request message including information associatedwith said ATM code; receiving, from said transaction management system,information identifying a list of available transaction accountsassociated with said account holder; transmitting, to said remotetransaction management system, information identifying a selectedtransaction account associated with said account holder for use in saidtransaction; and receiving, from said transaction management system,instructions to complete said transaction.
 2. The method of claim 1,wherein said ATM code is presented using at least one of: (i) analphanumeric code, (ii) a code consisting of a combination of letters,numbers or symbols, (iii) an encoded image including at least one of (a)a barcode, (b) a QR code, and (c) an image pattern, and (iv) a wirelesssignal.
 3. The method of claim 1, wherein said ATM code is a staticidentifier associated with a specific ATM at a specific location.
 4. Themethod of claim 1, wherein said ATM code is a dynamic identifiergenerated for said transaction and displayed via a display deviceassociated with said ATM.
 5. The method of claim 4, wherein said dynamicidentifier is generated by said ATM for use in said transaction.
 6. Themethod of claim 4, wherein said dynamic identifier is generated by saidtransaction management system for use in said transaction at said ATM.7. The method of claim 4, wherein said ATM code is generated to includeat least one of: (i) information identifying said ATM, (ii) atransaction type selected by said account holder, (iii) a transactionamount selected by said account holder, and (iv) an informationalmessage.
 8. The method of claim 7, wherein said causing an ATM code tobe captured by the mobile device further comprises: displayinginformation associated with said ATM code on a display device of saidmobile device.
 9. The method of claim 1, further comprising: receiving,from said transaction management system, information identifying a listof available transaction accounts associated with said account holderand a request for selection of at least one of said availabletransaction accounts.
 10. The method of claim 9, further comprisingdisplaying said list of available transaction accounts on a displaydevice of said mobile device, wherein said displaying said list ofavailable transaction accounts further comprises: displaying, for eachof said available transaction accounts, at least one of (i) an availablebalance, (ii) a transaction option available at said ATM using saidaccount, and (iii) offer information.
 11. The method of claim 10,wherein displaying said list of available transaction accounts furthercomprises: displaying, on a display device of said mobile device, saidlist of available transaction accounts in an order of preference,wherein said order is determined by at least one of (i) an accountholder rule, (ii) an ATM operator rule, (iii) a transaction managementsystem rule, and (iv) a financial institution rule.
 12. The method ofclaim 1, further comprising: receiving, from said transaction managementsystem, information identifying a set of transaction options availableto said account holder at said ATM and a request for selection of atleast one of said transaction options.
 13. The method of claim 12,wherein said information identifying a transaction option is determinedby at least one of (i) an account holder specified rule, (ii) an ATMoperator specified rule, and (iii) a system specified rule.
 14. Themethod of claim 1, further comprising: displaying, on a display deviceof said mobile device, a promotional message, said promotional messagebased on at least one of (i) an identity of an operator of the ATM, (ii)a location of the ATM, (iii) a profile of the customer, and (iv) thetransaction accounts used by the customer.
 15. The method of claim 1,further comprising: authenticating at least one of (i) said accountholder and (ii) said mobile device.
 16. The method of claim 15, whereinsaid authenticating said account holder is performed at least one of (i)prior to said causing an ATM code to be captured by the mobile device,and (ii) after said causing an ATM code to be captured by the mobiledevice.
 17. The method of claim 16, wherein said mobile device is asmart phone having an ATM transaction application installed in a memorythereof, wherein said authenticating said account holder furthercomprises: prompting said account holder for a passcode, said passcodeauthenticating said account holder to said ATM transaction application.18. The method of claim 16, wherein said authenticating said accountholder further comprises: verifying an identity of said account holderbased on at least one of: (i) a user identifier and password, (ii) apersonal identification number, (iii) a mobile telephone number, (iv) afacial recognition, and (v) a keyboard biometric process.
 19. The methodof claim 16, wherein said mobile device is a Web-enabled phone, whereinsaid authenticating said account holder further comprises: pointing abrowser of said mobile device to a Web page associated with saidtransaction management system; and prompting said account holder for apasscode, said passcode authenticating said account holder to saidtransaction management system.
 20. The method of claim 15, wherein saidauthenticating said mobile device is performed at least one of (i) priorto authenticating said account holder, and (ii) after authenticatingsaid account holder.
 21. The method of claim 15, wherein saidauthenticating said mobile device further comprises: establishing aconnection between said mobile device and said transaction managementsystem, wherein said transaction management system is operable tocompare authentication data associated with said mobile device withstored data associated with the mobile device.
 22. The method of claim21, wherein said mobile device authentication data includes at least oneof: (i) a mobile phone number, (ii) a unique identifier associated withan application installed on said mobile device, and (iii) a uniqueidentifier associated with said mobile device.
 23. The method of claim22, wherein said unique identifier associated with said mobile device isat least one of: (i) a hardware identifier, (ii) a serial number, (iii)a MAC address, (iv) an ASIN, and (v) a UUID.
 24. The method of claim 1,wherein said instructions to complete said transaction further comprise:a temporary code for entry into said ATM to complete said transaction,wherein said transaction management system transmits said temporary codeto said ATM to allow said transaction to occur.
 25. The method of claim1, wherein said instructions to complete said transaction furthercomprise: prompting said account holder to interact with a data inputdevice of said ATM to select a transaction type and transaction details,wherein said transaction management system transmits authorizationinformation to said ATM to allow said transaction to occur.
 26. Atransaction system, comprising: a mobile device, said mobile deviceassociated with an account holder and an automated teller machine(“ATM”) in communication with a transaction management system, saidtransaction management system configured to cause an ATM code to begenerated in response to a request from said ATM; transmit said ATM codeto said ATM; receive, from said mobile device, a transaction requestmessage including information associated with said ATM code, informationassociated with said account holder and information associated with saidmobile device, said information usable to identify a transaction to beconducted at said ATM; transmit, to said mobile device, informationidentifying a list of available transaction accounts associated withsaid account holder; receive, from said mobile device, informationidentifying a selected transaction account for use in said transaction;and transmit, to said ATM, instructions to complete said transaction forsaid account holder.